Device initialization by an access-restricted virtual machine

ABSTRACT

Device initialization by an access-restricted virtual machine, including: restricting access by a first operating system to a device during one or more device initialization operations, wherein the first operating system is executing in a first virtual machine supported by a hypervisor; determining, by a second operating system executing in a second virtual machine supported by the hypervisor, one or more modifications attempted by the first operating system to the device; and performing, by the second operating system, the one or more modifications to the device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority to U.S. patent application Ser. No. 16/382,583, filed Apr. 12, 2019, which is hereby incorporated by reference in its entirety.

BACKGROUND Field of the Invention

The field of the invention is data processing, or, more specifically, methods, apparatus, autonomous vehicles, and products for device operation across multiple operating system modalities.

Description of Related Art

Devices may require device drivers to operate. One portion of the device driver may include code or processor-executable instructions to perform one or more device initialization operations to place the device in an initialized state. Another portion of the device driver may include code or processor-executable instructions to perform device operations once the device is in an initialized state. Where the device is to be used by a formally verified operating system, the amount of code used by the formally verified operating system increases the complexity in achieving formal verification.

SUMMARY

Device operation across multiple operating system modalities may include performing, by a first virtual machine comprising a first operating system, one or more device initialization operations for a device; determining that the device is in an initialized state; and performing, by a second virtual machine comprising a second operating system, one or more device operations of the device in the initialized state.

The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows example views of an autonomous vehicle for device operation across multiple operating system modalities.

FIG. 2 is block diagram of an autonomous computing system for device operation across multiple operating system modalities.

FIG. 3 is a block diagram of a redundant power fabric for device operation across multiple operating system modalities.

FIG. 4 is a block diagram of a redundant data fabric for device operation across multiple operating system modalities.

FIG. 5 is an example view of process allocation across CPU packages for device operation across multiple operating system modalities.

FIG. 6 is a flowchart of an example method for device operation across multiple operating system modalities.

FIG. 7 is a flowchart of an example method for device operation across multiple operating system modalities.

FIG. 8 is a flowchart of an example method for device operation across multiple operating system modalities.

DETAILED DESCRIPTION

Example methods, apparatus, autonomous vehicles, and products for device operation across multiple operating system modalities are described with reference to the accompanying drawings, beginning with FIG. 1 . FIG. 1 shows multiple views of an autonomous vehicle 100 configured to carry out operating system modality switching in accordance with some embodiments of the present disclosure. Right side view 101 a shows a right side of the autonomous vehicle 100, where sensors 102 and 103 are mounted on or otherwise affixed to the right side of the autonomous vehicle 100. The sensors 102 and 103 that are mounted on or otherwise affixed to the autonomous vehicle 100 may be configured to capture image data, video data, audio data, or any other data (including combinations thereof) that can be used to determine the environmental state of the autonomous vehicle 100 from the perspective of the right side of the autonomous vehicle 100.

Front view 101 b shows a front side of the autonomous vehicle 100, where sensors 104 and 106 are mounted on or otherwise affixed to the front side of the autonomous vehicle 100. The sensors 104 and 106 that are mounted on or otherwise affixed to the front side of the autonomous vehicle 100 may be configured to capture image data, video data, audio data, or any other data (including combinations thereof) that can be used to determine the environmental state of the autonomous vehicle 100 from the perspective of the front side of the autonomous vehicle 100.

Rear view 101 c shows a rear side of the autonomous vehicle 100, where sensors 108 and 110 are mounted on or otherwise affixed to the rear side of the autonomous vehicle 100. The sensors 108 and 110 that are mounted on or otherwise affixed to the rear side of the autonomous vehicle 100 may be configured to capture image data, video data, audio data, or any other data (including combinations thereof) that can be used to determine the environmental state of the autonomous vehicle 100 from the perspective of the rear side of the autonomous vehicle 100.

Top view 101 d shows an overhead view of the autonomous vehicle 100. Shown in the top view 101 d are sensors 102-110 as illustrated in previous views, as well as sensors 112 and 114 that are mounted on or otherwise affixed to the left side of the autonomous vehicle 100. The sensors 112 and 114 that are mounted on or otherwise affixed to the left side of the autonomous vehicle 100 may be configured to capture image data, video data, audio data, or any other data (including combinations thereof) that can be used to determine the environmental state of the autonomous vehicle 100 from the perspective of the left side of the autonomous vehicle 100. Readers will appreciate that the placement of the sensors 102-114 is merely for illustrative purposes and in no way represents a limitation on the arrangement of sensors, the manner in which the sensors are attached to the autonomous vehicle 100, and so on.

Further shown in the top view 101 d is an automation computing system 116. The automation computing system 116 can include one or more computing devices configured to evaluate the environmental state of the autonomous vehicle 100, control one or more autonomous operations (e.g., autonomous driving operations) of the autonomous vehicle 100 in coordination with other components of the autonomous vehicle 100, and perform other tasks as will be explained in greater detail below. In such an example, the one or more computing devices may be configured to control one or more autonomous operations of the autonomous vehicle 100 through the use of one or more modules of computer program instructions that are executing on one or more of the computing devices. For example, the automation computing system 116 may be configured to process sensor data (e.g., data from the sensors 102-114 and potentially other sensors), operational data (e.g., a speed, acceleration, gear, orientation, turning direction), and other data to determine an operational state and/or operational history of the autonomous vehicle. The automation computing system 116 may then determine one or more operational commands for the autonomous vehicle (e.g., a change in speed or acceleration, a change in brake application, a change in gear, a change in turning or orientation, etc.) that may be effected via coordination between the automation computing system 116 and other components within the autonomous vehicle 100. For example, the automation computing system 116 may be coupled, directly or indirectly, for data communications with a device that can control the operation of a steering system within the autonomous vehicle 100. In such an example, if an analysis of sensor data causes the automation computing system 116 to determine that the direction of the autonomous vehicle 100 should be altered, the automation computing system 116 may issue one or more commands to the device that can control the operation of the steering system within the autonomous vehicle 100, thereby causing the device that can control the operation of a steering system within the autonomous vehicle 100 to change the direction of the autonomous vehicle by manipulating the steering system within the autonomous vehicle 100. The automation computing system 116 may also capture and store sensor data. Operational data of the autonomous vehicle may also be stored in association with corresponding sensor data, thereby indicating the operational data of the autonomous vehicle 100 at the time the sensor data was captured.

Although the autonomous vehicle 100 of FIG. 1 is shown as car, it is understood that autonomous vehicles 100 in accordance with embodiments of the present disclosure may also include other vehicles, including motorcycles, planes, helicopters, unmanned aerial vehicles (UAVs, e.g., drones), or other vehicles as can be appreciated. Moreover, it is understood that additional sensors or other external sensors may also be included in the autonomous vehicle 100.

For further explanation, FIG. 2 sets forth a block diagram of automated computing machinery comprising an exemplary automation computing system 116 according to some embodiments of the present disclosure. The automation computing system 116 of FIG. 2 includes at least one computer Central Processing Unit (‘CPU’) package 204 as well as random access memory 206 (‘RAM’) which is connected through a data communications link (e.g., a bus) to the CPU packages 204 and to other components of the automation computing system 116.

A CPU package 204 may comprise a plurality of processing units. For example, each CPU package 204 may comprise a logical or physical grouping of a plurality of processing units. Each processing unit may be allocated a particular process for execution. Moreover, each CPU package 204 may comprise one or more redundant processing units. A redundant processing unit is a processing unit not allocated a particular process for execution unless a failure occurs in another processing unit. For example, when a given processing unit allocated a particular process fails, a redundant processing unit may be selected and allocated the given process. A process may be allocated to a plurality of processing units within the same CPU package 204 or different CPU packages 204. For example, a given process may be allocated to a primary processing unit in a CPU package 204. The results or output of the given process may be output from the primary processing unit to a receiving process or service. The given process may also be executed in parallel on a secondary processing unit. The secondary processing unit may be included within the same CPU package 204 or a different CPU package 204. The secondary processing unit may not provide its output or results of the process until the primary processing unit fails. The receiving process or service may then receive data from the secondary processing unit and a redundant processing unit may then be selected and have allocated the given process to ensure that two or more processing units are allocated the given process for redundancy and increased reliability.

The CPU packages 204 are communicatively coupled to one or more sensors 212. The sensors 212 may be configured to capture sensor data describing the operational and environmental conditions of an autonomous vehicle. For example, the sensors 212 may include sensors (e.g., the sensors 102-114 of FIG. 1 ), accelerometers, Global Positioning System (GPS) radios, Lidar sensors, or other sensors as can be appreciated. Although the sensors 212 are shown as being external to the automation computing system 116, it is understood that one or more of the sensors 212 may reside as a component of the automation computing system 212 (e.g., on the same board, within the same housing or chassis). The sensors 212 may be communicatively coupled with the CPU packages 204 via a switched fabric 213.

The switched fabric 213 comprises a communications topology through which the CPU packages 204 and sensors 212 are coupled via a plurality of switching mechanisms (e.g., latches, switches, crossbar switches, field programmable gate arrays (FPGAs), etc.). For example, the switched fabric 213 may implement a mesh connection connecting the CPU packages 204 and sensors 212 as endpoints, with the switching mechanisms serving as intermediary nodes of the mesh connection. The CPU packages 204 and sensors 212 may be in communication via a plurality of switched fabrics 213. For example, each of the switched fabrics 213 may include the CPU packages 204 and sensors 212, or a subset of the CPU packages 204 and sensors 212, as endpoints. Each switched fabric 213 may also comprise a respective plurality of switching components. The switching components of a given switched fabric 213 may be independent (e.g., not connected) of the switching components of other switched fabrics 213 such that only switched fabric 213 endpoints (e.g., the CPU packages 204 and sensors 212) are overlapping across the switched fabrics 213. This provides redundancy such that, should a connection between a CPU package 204 and sensor 212 fail in one switched fabric 213, the CPU package 204 and sensor 212 may remain connected via another switched fabric 213. Moreover, in the event of a failure in a CPU package 204, a processor of a CPU package 204, or a sensor, a communications path excluding the failed component and including a functional redundant component may be established.

The CPU packages 204 and sensors 212 are configured to receive power from one or more power supplies 215. The power supplies 215 may comprise an extension of a power system of the autonomous vehicle 100 or an independent power source (e.g., a battery). The power supplies 215 may supply power to the CPU packages 204 and sensors 212 by another switched fabric 214. The switched fabric 214 provides redundant power pathways such that, in the event of a failure in a power connection, a new power connection pathway may be established to the CPU packages 204 and sensors 214.

Stored in RAM 206 is an automation module 220. The automation module 220 may be configured to process sensor data from the sensors 212 to determine one or more operational commands for an autonomous vehicle 100 to affect the movement, direction, or other function of the autonomous vehicle 100, thereby facilitating autonomous driving or operation of the vehicle. Such operational commands may include a change in the speed of the autonomous vehicle 100, a change in steering direction, a change in gear, or other command as can be appreciated. For example, the automation module 220 may provide sensor data and/or processed sensor data as one or more inputs to a trained machine learning model (e.g., a trained neural network) to determine the one or more operational commands. The operational commands may then be communicated to autonomous vehicle control systems 223 via a vehicle interface 222. The autonomous vehicle control systems 223 are configured to affect the movement and operation of the autonomous vehicle 100. For example, the autonomous vehicle control systems 223 may turn or otherwise change the direction of the autonomous vehicle 100, accelerate or decelerate the autonomous vehicle 100, change a gear of the autonomous vehicle 100, or otherwise affect the movement and operation of the autonomous vehicle 100.

In the example depicted in FIG. 2 , a data collection module 224 configured to process and/or store sensor data received from the one or more sensors 212 is depicted as being stored in RAM. The data collection module 224 may be configured to store the sensor data as captured by the one or more sensors 212, or processed sensor data 212 (e.g., sensor data 212 having object recognition, compression, depth filtering, or other processes applied). Such processing may be performed by the data collection module 224 in real-time or in substantially real-time as the sensor data is captured by the one or more sensors 212. The processed sensor data may then be used by other functions or modules. For example, the automation module 220 may use processed sensor data as input to determine one or more operational commands. The data collection module 224 may store the sensor data in data storage 218.

Also stored in RAM 206 is a data processing module 226. The data processing module 226 is configured to perform one or more processes on stored sensor data (e.g., stored in data storage 218 by the data collection module 218) prior to upload to a server 227. Such operations can include filtering, compression, encoding, decoding, or other operations as can be appreciated. The data processing module 226 may then communicate the processed and stored sensor data to the server 227. Readers will appreciate that although the embodiment depicted in FIG. 2 relates to an embodiment where the data processing module 226 communicates the processed and stored sensor data to the server 227, in other embodiments, the data processing module 226 may communicate with other types of environments such a cloud computing environment, data warehouse, or any other endpoint that may receive data from the autonomous vehicle 100.

Further stored in RAM 206 is a hypervisor 228. The hypervisor 228 is configured to manage the configuration and execution of one or more virtual machines 229. For example, each virtual machine 229 may emulate and/or simulate the operation of a computer. Accordingly, each virtual machine 229 may comprise a guest operating system 216 for the simulated computer. The hypervisor 228 may manage the creation of a virtual machine 229 including installation of the guest operating system 216. The hypervisor 228 may also manage when execution of a virtual machine 229 begins, is suspended, is resumed, or is terminated. The hypervisor 228 may also control access to computational resources (e.g., processing resources, memory resources, device resources) by each of the virtual machines.

Each of the virtual machines 229 may be configured to execute one or more of the automation module 220, the data collection module 224, the data processing module 226, or combinations thereof. Moreover, as is set forth above, each of the virtual machines 229 may comprise its own guest operating system 216. Guest operating systems 216 useful in autonomous vehicles in accordance with some embodiments of the present disclosure include UNIX™, Linux™, Microsoft Windows™, AIX™, IBM's i OS™, and others as will occur to those of skill in the art. For example, the autonomous vehicle 100 may be configured to execute a first operating system when the autonomous vehicle is in an autonomous (or even partially autonomous) driving mode and the autonomous vehicle 100 may be configured to execute a second operating system when the autonomous vehicle is not in an autonomous (or even partially autonomous) driving mode. In such an example, the first operating system may be formally verified, secure, and operate in real-time such that data collected from the sensors 212 are processed within a predetermined period of time, and autonomous driving operations are performed within a predetermined period of time, such that data is processed and acted upon essentially in real-time. Continuing with this example, the second operating system may not be formally verified, may be less secure, and may not operate in real-time as the tasks that are carried out (which are described in greater detail below) by the second operating system are not as time-sensitive the tasks (e.g., carrying out self-driving operations) performed by the first operating system.

Readers will appreciate that although the example included in the preceding paragraph relates to an embodiment where the autonomous vehicle 100 may be configured to execute a first operating system when the autonomous vehicle is in an autonomous (or even partially autonomous) driving mode and the autonomous vehicle 100 may be configured to execute a second operating system when the autonomous vehicle is not in an autonomous (or even partially autonomous) driving mode, other embodiments are within the scope of the present disclosure. For example, in another embodiment one CPU (or other appropriate entity such as a chip, CPU core, and so on) may be executing the first operating system and a second CPU (or other appropriate entity) may be executing the second operating system, where switching between these two modalities is accomplished through fabric switching, as described in greater detail below. Likewise, in some embodiments, processing resources such as a CPU may be partitioned where a first partition supports the execution of the first operating system and a second partition supports the execution of the second operating system.

The guest operating systems 216 may correspond to a particular operating system modality. An operating system modality is a set of parameters or constraints which a given operating system satisfies, and are not satisfied by operating systems of another modality. For example, a given operating system may be considered a “real-time operating system” in that one or more processes executed by the operating system must be performed according to one or more time constraints. For example, as the automation module 220 must make determinations as to operational commands to facilitate autonomous operation of a vehicle. Accordingly, the automation module 220 must make such determinations within one or more time constraints in order for autonomous operation to be performed in real time. The automation module 220 may then be executed in an operating system (e.g., a guest operating system 216 of a virtual machine 229) corresponding to a “real-time operating system” modality. Conversely, the data processing module 226 may be able to perform its processing of sensor data independent of any time constrains, and may then be executed in an operating system (e.g., a guest operating system 216 of a virtual machine 229) corresponding to a “non-real-time operating system” modality.

As another example, an operating system (e.g., a guest operating system 216 of a virtual machine 229) may comprise a formally verified operating system. A formally verified operating system is an operating system for which the correctness of each function and operation has been verified with respect to a formal specification according to formal proofs. A formally verified operating system and an unverified operating system (e.g., one that has not been formally verified according to these proofs) can be said to operate in different modalities.

The automation module 220, data collection module 224, data collection module 224, data processing module 226, hypervisor 228, and virtual machine 229 in the example of FIG. 2 are shown in RAM 206, but many components of such software typically are stored in non-volatile memory also, such as, for example, on data storage 218, such as flash storage. Moreover, any of the automation module 220, data collection module 224, and data processing module 226 may be executed in a virtual machine 229 and facilitated by a guest operating system 216 of that virtual machine 229.

The exemplary automation computing system 116 of FIG. 2 includes a communications adapter 238 for data communications with other computers and for data communications with a data communications network. Such data communications may be carried out through data communications networks such as IP data communications networks, and in other ways as will occur to those of skill in the art. Communications adapters implement the hardware level of data communications through which one computer sends data communications to another computer, directly or through a data communications network. Examples of communications adapters useful in autonomous vehicle according to some embodiments of the present disclosure include 802.11 adapters for wireless data communications, mobile adapters (e.g., 4G communications adapters, LTE communications adapters, 5G communications adapters) for mobile data communications, and others. For example, the automation computing system 116 may communicate with one or more remotely disposed servers 227, or other communications endpoint as described above, via the communications adapter 238.

The exemplary automation computing system of FIG. 2 also includes one or more Artificial Intelligence (AI) accelerators 240. The AI accelerator 240 provides hardware-based assistance and acceleration of AI-related functions, including machine learning, computer vision, etc. Accordingly, performance of any of the automation module 220, data collection module 224, data processing module 226, or other operations of the automation computing system 116 may be performed at least in part by the AI accelerators 240.

The exemplary automation computing system of FIG. 2 also includes one or more graphics processing units (GPUs) 242. The GPUs 242 are configured to provide additional processing and memory resources for processing image and/or video data, including encoding, decoding, etc. Accordingly, performance of any of the automation module 220, data collection module 224, data processing module 226, or other operations of the automation computing system 116 may be performed at least in part by the GPUs 242.

FIG. 3 shows an example redundant power fabric for an autonomous vehicle having a redundant processor fabric. The redundant power fabric provides redundant pathways for power transfer between the power supplies 215, the sensors 212, the CPU packages 204, and may also be used for power transfer to other components not explicitly depicted in FIG. 3 . In this example, the power supplies 215 are coupled to the sensors 212 and CPU packages via two switched fabrics 214 a and 214 b, although additional redundant resources may be incorporated in accordance with other embodiments of the present disclosure. The topology shown in FIG. 3 provides redundant pathways between the power supplies 215, the sensors 212, and the CPU packages 204 such that power can be rerouted through any of multiple pathways in the event of a failure in an active connection pathway. The switched fabrics 214 a and 214 b may provide power to the sensors 212 using various connections, including Mobile Industry Processor Interface (MIPI), Inter-Integrated Circuit (I2C), Universal Serial Bus (USB), or another connection. The switched fabrics 214 a and 214 b may also provide power to the CPU packages 204 using various connections, including Peripheral Component Interconnect Express (PCIe), USB, or other connections. Although only two switched fabrics 214 a and 214 b are shown connecting the power supplies 215 to the sensors 212 and CPU packages 204, it is understood that the approach shown by FIG. 3 can be modified to include additional switched fabrics 214.

FIG. 4 is an example redundant data fabric for an autonomous vehicle having a redundant processor fabric. The redundant data fabric provides redundant data connection pathways between sensors 212 and CPU packages 204, and may also provide redundant data connection pathways between other components not explicitly depicted in FIG. 4 . In this example view, three CPU packages 204 a, 204 b, and 204 c are connected to three sensors 212 a, 212 b, and 212 c via three switched fabrics 213 a, 213 b, and 213 c. Each CPU package 204 a, 204 b, and 204 c is connected to a subset of the switched fabrics 213 a, 213 b, and 213 c. For example, CPU package 204 a is connected to switched fabrics 213 a and 213 c, CPU package 204 b is connected to switched fabrics 213 a and 213 b, and CPU package 204 c is connected to switched fabrics 213 b and 213 c. Each switched fabric 213 a, 213 b, and 213 c is connected to a subset of the sensors 212 a, 212 b, and 212 c. For example, switched fabric 213 a is connected to sensors 212 a and 212 b, switched fabric 213 b is connected to sensor 212 b and 212 c, and switched fabric 213 c is connected to sensors 212 a and 212 c. Under this topology, each CPU package 204 a, 204 b, and 204 c has an available connection path to any sensor 212 a, 212 b, and 212 c. It is understood that the topology of FIG. 4 is exemplary, and that CPU packages, switched fabrics, sensors, or connections between components may be added or removed while maintaining redundancy as can be appreciated by one skilled in the art.

FIG. 5 is an example view of process allocation across CPU packages for a redundant processing fabric in an autonomous vehicle. Shown are three CPU packages 204 a, 204 b, and 204 c. Each CPU package 204 a includes a processing unit that has been allocated (e.g., by a hypervisor 228 or other process or service) primary execution of a process and another processing unit that has been allocated secondary execution of a process. As set forth herein, primary execution of a process describes an executing instance of a process whose output will be provided to another process or service. Secondary execution of the process describes executing an instance of the process in parallel to the primary execution, but the output may not be output to the other process or service. For example, in CPU package 204 a, processing unit 502 a has been allocated secondary execution of “process B,” denoted as secondary process B 504 b, while processing unit 502 b has been allocated primary execution of “process C,” denoted as primary process C 506 a.

CPU package 204 a also comprises two redundant processing units that are not actively executing a process A, B, or C, but are instead reserved in case of failure of an active processing unit. Redundant processing unit 508 a has been reserved as “AB redundant,” indicating that reserved processing unit 508 a may be allocated primary or secondary execution of processes A or B in the event of a failure of a processing unit allocated the primary or secondary execution of these processes. Redundant processing unit 508 b has been reserved as “A/C redundant,” indicating that reserved processing unit 508 b may be allocated primary or secondary execution of processes A or C in the event of a failure of a processing unit allocated the primary or secondary execution of these processes.

CPU package 204 b includes processing unit 502 c, which has been allocated primary execution of “process A,” denoted as primary process A 510 a, and processing unit 502 d, which has been allocated secondary execution of “process C,” denoted as secondary process C 506 a. CPU package 204 b also includes redundant processing unit 508 c, reserved as “AB redundant,” and redundant processing unit 508 d, reserved as “B/C redundant.” CPU package 204 c includes processing unit 502 e, which has been allocated primary execution of “process B,” denoted as primary process B 504 a, and processing unit 502 f, which has been allocated secondary execution of “process A,” denoted as secondary process A 510 a. CPU package 204 c also includes redundant processing unit 508 e, reserved as “B/C redundant,” and redundant processing unit 508 f, reserved as “A/C redundant.”

As set forth in the example view of FIG. 5 , primary and secondary instances of processes A, B, and C are each executed in an allocated processing unit. Thus, if a processing unit performing primary execution of a given process fails, the processing unit performing secondary execution may instead provide output of the given process to a receiving process or service. Moreover, the primary and secondary execution of a given process are executed on different CPU packages. Thus, if an entire processing unit fails, execution of each of the processes can continue using one or more processing units handling secondary execution. The redundant processing units 508 a-f allow for allocation of primary or secondary execution of a process in the event of processing unit failure. This further prevents errors caused by processing unit failure as parallel primary and secondary execution of a process may be restored. One skilled in the art would understand that the number of CPU packages, processing units, redundant processing units, and processes may be modified according to performance requirements while maintaining redundancy.

For further explanation, FIG. 6 sets forth a flow chart illustrating an exemplary method for device operation across multiple operating system modalities that includes performing 602, by a first operating system 616, one or more device initialization operations for a device 620 a, 620 b, 620 n. The devices 620 a, 620 b, 620 n depicted in FIG. 6 may be included in an autonomous vehicle 600 that is similar to the autonomous vehicles described above and may include, for example, one or more image sensors that are affixed to the autonomous vehicle 600, a GPS receiver that is included in the autonomous vehicle 600, an accelerometer that is included in the autonomous vehicle 600, computing devices and peripherals that are included in the autonomous vehicle 600, and many other types of devices.

The first operating system 616 may be embodied, for example, as a non-verified operating system (e.g., an operating system that has not been subjected to formal verification) that is executing within a first virtual machine 612 that is supported by a hypervisor 610. In fact, the first operating system 616 may be embodied as a standard Linux operating system that can provide a file system, an IP stack, and other standard operating system offerings. In such an example, a portion of driver code for the device corresponding to the one or more device initialization operations may be executed by the first operating system 616. The one or more device initialization operations comprise one or more operations that must be performed in order for the device to perform its designated operations (e.g., component configuration, preference or configuration file loading and implementation, diagnostics or troubleshooting operations).

Performing 602 the one or more device initialization operations may be carried out in a variety of ways. For example, the first operating system 616 that is executing on the first virtual machine 612 may include device drivers and similar software components that are used to initialize a plurality of devices. In such an example, the first operating system 616 may perform 602 the one or more device initialization operations by executing the device drivers (or at least the portion of the device driver that contains initialization code) or similar software components for some set of the devices 620 a, 620 b, 620 n that are utilized by the autonomous vehicle 600, or at least those devices 620 a, 620 b, 620 n that are utilized to facilitate autonomous driving operations. In one embodiment, the devices 620 a, 620 b, 620 n may initially be accessed only by the first operating system 616 during the initialization process and, once initialized, the first operating system 616 and the devices 620 a, 620 b, 620 n may be blocked from communicating. In another example, the first operating system 616 may perform 602 the one or more device initialization operations by modifying one or more device registers of the device. For example, the first operating system 616 may have restricted access (e.g., excluding write access) to the one or more device registers. In such an example, any attempted modification by the first operating system 616 to the one or more device registers may trigger a fault handling operation that indicates, to a second operating system 618 (e.g., a formally verified operating system) that is executing in a second virtual machine 614, the one or more attempted modifications. The second operating system 618 may then perform the one or more attempted modifications. Readers will appreciate that performing 602 the one or more device initialization operations may be carried out, in some embodiments, as the result of communications between the device 620 a, 620 b, 620 n and one of the virtual machines 612, 614 as the virtual machines 612, 614 may provide the interfaces between the operating systems 616, 618 and the device 620 a, 620 b, 620 n.

The method of FIG. 6 further comprises determining 604 that the device 620 a, 620 b, 620 n is in an initialized state. Determining that the device 620 a, 620 b, 620 n is in an initialized state may be performed by the second operating system 618 or, in other embodiments, by some other entity. Determining 604 that the device 620 a, 620 b, 620 n is in an initialized state may be performed in response to a message or signal sent from the first operating system 616 to the second operating system 618 via the hypervisor that indicates that the first operating system 616 believes that it has initialized the device 620 a, 620 b, 620 n. In such a way, a trust relationship can be established where the first operating system 616 attempts to perform some device initialization operations and the second operating system 618 attempts to verify that the device initialization operations have actually been performed. If the second operating system 618 affirmatively determines that the device 620 a, 620 b, 620 n is in the initialized state, the second operating system 618 may send a signal or message to the hypervisor 610 indicating that the device is in the initialized state, such that they hypervisor may block any subsequent attempted data communications between the device 620 a, 620 b, 620 n and the first operating system 616. Where the first operating system 616 had access (e.g., at least write access) to the one or more device registers to allow the first operating system 616 to perform the one or more device initialization operations, the hypervisor 610 may remove, in response to the device being in the initialized state, the access by the first operating system 616 to the one or more device registers.

In response to the device being in the initialized state, the second operating system 618 (e.g., the formally verified guest operating system 216) may perform 606 one or more device operations of the device 620 a, 620 b, 620 n in the initialized state (e.g., causing the device to generate data (e.g., sensor data), performing input/output operations associated with the device, performing further modifications to device registers, and so on). Readers will appreciate that performing 606 one or more device operations of the device 620 a, 620 b, 620 n in the initialized state may be carried out, in some embodiments, as the result of communications between the device 620 a, 620 b, 620 n and the second virtual machine 614 as the second virtual machine 614 may provide the interfaces between the second operating system 618 and the device 620 a, 620 b, 620 n.

Although the example depicted in FIG. 6 relates to an embodiment where a first operating system 616 that is executing on a first virtual machine 612 performs 602 one or more device initialization operations for a device 620 a, 620 b, 620 n, a second operating system 618 that is executing on a second virtual machine 614 determines 604 that the device 620 a, 620 b, 620 n is in an initialized state, and the second operating system 618 performs 606 one or more device operations of the device in the initialized state, in other embodiments such actions may be carried out by different actors. Consider an example in which one CPU (or other appropriate entity such as a chip, CPU core, and so on) is executing the first operating system 616 and a second CPU (or other appropriate entity) is executing the second operating system 618, where switching between the different operating systems 616, 618 is accomplished through fabric switching. In such an example, the first operating system 616 executing on the first CPU can perform 602 the one or more device initialization operations for a device 620 a, 620 b, 620 n, and the second operating system 618 that is executing on a second CPU may be responsible for determining 604 that the device 620 a, 620 b, 620 n is in an initialized state and performing 606 one or more device operations of the device in the initialized state, with no assistance from a hypervisor. In a similar fashion, for embodiments where the two operating systems 616, 618 are executing on distinct partitions a hardware resource, the steps described above may be performed by the appropriate operating system 616, 618, with no assistance from a hypervisor.

For further explanation, FIG. 7 sets forth a flow chart illustrating an exemplary method for device operation across multiple operating system modalities that includes performing 602, by a first operating system 616, one or more device initialization operations for a device 620 a, 620 b, 620 n; determining 604 that the device 620 a, 620 b, 620 n is in an initialized state 604; and performing, by a second operating system 618, one or more device operations of the device 620 a, 620 b, 620 n in the initialized state.

FIG. 7 differs from FIG. 6 in that determining 604 that the device 620 a, 620 b, 620 n is in an initialized state comprises determining 702 that the one or more device registers are in an initialized state. For example, determining 702 that the one or more device registers are in the initialized state may include determining whether any value, or a predefined value, is stored in each of the one or more device registers. Determining 702 that the one or more device registers are in the initialized state may be performed by the second operating system 618 or by another entity. Determining 702 that the one or more device registers are in the initialized state may be performed in response to a signal or message from the first operating system 616 that is sent to the second operating system 618 via the hypervisor 610 indicating that the first operating system 616 believes that it has successfully performed the one or more device initialization operations. Readers will appreciate that in some embodiments, determining 604 that the device 620 a, 620 b, 620 n is in an initialized state can be carried out in ways other than examining the device registers. For example, the device 620 a, 620 b, 620 n may be determined 604 to be in an initialized state when the device 620 a, 620 b, 620 n becomes available for data communications, the device 620 a, 620 b, 620 n may be determined 604 to be in an initialized state when the device 620 a, 620 b, 620 n sends a signal indicating that it is initialized, and in many other ways.

FIG. 7 further differs from FIG. 6 in that the method of FIG. 7 further comprises removing 704, by the hypervisor 610, access by the first operating system 616 to the one or more device registers of the device. The hypervisor 610 may remove 704 access by the first operating system 616 to the one or more device registers of the device in response to the hypervisor 610 determining (e.g., via a message from the second operating system 618) that the device 620 a, 620 b, 620 n is in an initialized state. For example, the hypervisor 610 may remove access by the first operating system 616 to the one or more device registers in response to a determination by the second operating system 618 that the device is in an initialized state. In other words, access rights granted by the hypervisor 610 to the first operating system 616 facilitating the performance of the one or more device initialization operations are removed in response to the device 620 a, 620 b, 620 n being in the initialized state.

Readers will appreciate that in some embodiments, the hypervisor 610 may remove access by the first operating system 616 to the device generally—not just removing access to the device registers. For example, the hypervisor 610 may block all data communications between the device 620 a, 620 b, 620 n and the first operating system 616, the hypervisor 610 may block the first operating system 616 from performing any device initialization or modification operations, and so on. Readers will further appreciate that although the example method depicted in FIG. 7 illustrates an embodiment where the first operating system 616 loses access to the devices 620 a, 620 b, 620 n prior to the second operating system 618 determining 604 that the devices 620 a, 620 b, 620 n are in an initialized state, these steps may be performed in reverse order in some embodiments.

Although the example depicted in FIG. 7 relates to an embodiment where a second operating system 618 that is executing in a second virtual machine 614 determines 702 that the one or more device registers are in the initialized state and a hypervisor removes 704 access by the first operating system 616 to the one or more device registers of the device, in other embodiments such actions may be carried out by different actors. Consider an example in which one CPU (or other appropriate entity such as a chip, CPU core, and so on) is executing the first operating system 616 and a second CPU (or other appropriate entity) is executing the second operating system 618, where switching between the different operating systems 616, 618 is accomplished through fabric switching. In such an example, the second operating system 618 that is executing on a second CPU may be responsible for determining 702 that the one or more device registers are in the initialized state and removing 704 access by the first operating system 616 to the one or more device registers of the device may be carried out through fabric switching, with no assistance from a hypervisor. In a similar fashion, for embodiments where the two operating systems 616, 618 are executing on distinct partitions a hardware resource, the steps described above may be performed as described in the preceding sentence.

For further explanation, FIG. 8 sets forth a flow chart illustrating an exemplary method for device operation across multiple operating system modalities that includes performing 602, by a first operating system 616, one or more device initialization operations for a device 620 a, 620 b, 620 n; determining 604 that the device is in an initialized state 604; and performing, by a second operating system 618, one or more device operations of the device 620 a, 620 b, 620 n in the initialized state.

In the example method depicted in FIG. 8 , performing 602, by a first operating system 616, one or more device initialization operations for a device 620 a, 620 b, 620 n includes attempting 802, by the first operating system 616, the one or more modifications to the device 620 a, 620 b, 620 n. The first operating system 616 may attempt 802 the one or more modifications to the device 620 a, 620 b, 620, for example, by issuing one or more commands/requests to perform some device initialization operation on the device 620 a, 620 b, 620 n. In such an example, however, the hypervisor 610 (or some other entity, including the device itself) may block the performance of such device initialization operations. For example, the first operating system 616 may believe that it has the adequate permissions to perform such device initialization operations, but the hypervisor 610 or even the device 620 a, 620 b, 620 n itself may have a permission set that allows only the second operating system 618 (e.g., the formally verified operating system) to actually initiate the performance of such device initialization operations.

The example method depicted in FIG. 8 also includes restricting 804, by a hypervisor 610, access by the first operating system 616 to the device 620 a, 620 b, 620 n. The hypervisor 610 may restrict 804 access by the first operating system 616 to the device 620 a, 620 b, 620 n, for example, by restricting access to the device registers of the device 620 a, 620 b, 620 n, by blocking any attempted data communications between the device 620 a, 620 b, 620 n and the first operating system 616, by preventing the execution of device initialization/modification operations issued by the first operating system 616 to the device 620 a, 620 b, 620 n, and so on.

The example method depicted in FIG. 8 also includes performing 806, in response to the first operating system 616 attempting 802 the one or more modifications to the device 620 a, 620 b, 620 n, a fault handling operation indicating, to the second operating system 618, the one or more attempted modifications. In such an example, the hypervisor 610, the devices 620 a, 620 b, 620 n, or some other entity may be configured to issue a fault upon detecting that the first operating system 616 is attempting 802 one or more modifications to the device 620 a, 620 b, 620 n. In response to this fault, the hypervisor 610, the devices 620 a, 620 b, 620 n, or some other entity may be configured to perform a fault handling operation that essentially prevents the first operating system 616 from performing the one or more modifications to the device 620 a, 620 b, 620 n and also alerts the second operating system 618 that the first operating system 616 attempted 802 to perform one or more modifications to the device 620 a, 620 b, 620 n. In such an example, the fault handling operation may further be configured to send the second operating system 618 information describing the nature of the modifications to the device 620 a, 620 b, 620 n that the first operating system 616 attempted to perform, so that the second operating system 618 can (as appropriate) itself perform the modifications to the device 620 a, 620 b, 620 n that the first operating system 616 attempted to perform. By evaluating such information, the second operating system 618 can determine the one or more modifications attempted by the first operating system 616.

For example, in response to the first operating system 616 attempting the one or more modifications to the one or more device registers, a fault handling operation (e.g., of the hypervisor 610) may indicate, to the second operating system 618, the one or more attempted modifications. In other words, determining 808, by the second operating system 618, the one or more modifications attempted by the first operating system 616 to the one or more devices may comprise receiving an indication of the one or more modifications attempted by the first operating system 616 to the device from the fault handling operation. The second operating system 618 may maintain a state machine describing the one or more attempted modifications as indicated through subsequent fault handling operations.

The example method depicted in FIG. 8 also includes performing 810, by the second operating system 618, the one or more modifications attempted by the first operating system 616 to the device. As the second operating system 618 may have write access to the one or more device registers (e.g., as dictated by the hypervisor 610) or other appropriate permissions, no fault handling operations are triggered by the second operating system 618 modifying the device. Readers will appreciate that performing 810, by the second operating system 618, the one or more modifications attempted by the first operating system 616 to the device may be carried out, in some embodiments, as the result of communications between the device 620 a, 620 b, 620 n and the second virtual machine 614 as the second virtual machine 614 may provide the interfaces between the second operating system 618 and the device 620 a, 620 b, 620 n.

Although many of the embodiments described above relate to embodiments where operating systems with different characteristics (e.g., real-time versus non-real-time, formally verified versus non-formally verified) are run on the same hypervisor, other embodiments for providing access to operating systems with different characteristics are within the scope of the present disclosure. For example, in other embodiments one CPU (or other appropriate entity such as a chip, CPU core, and so on) may be executing the one operating system and a second CPU (or other appropriate entity) may be executing another operating system with different characteristics, where switching between the different operating systems is accomplished through fabric switching. In fact, in view of the fact that embodiments described herein may have multiple CPU packages as described above, some CPU packages may be executing one type of operating system (e.g., a real-time operating system) and other CPU packages may be executing other types of operating systems (e.g., a non-real-time operating system) at the same time. Likewise, in some embodiments, processing resources such as a CPU or CPU package may be partitioned (statically or dynamically) where a first partition supports the execution of one operating system and a second partition supports the execution of the operating system with different characteristics. In such a way, because there are multiple CPU packages and each CPU package may be running in a multi-modal state (e.g., within each CPU package various partitions are running different operating systems), the cluster of CPU packages may provide for a distributed multi-modal system.

Readers will further appreciate that the different characteristics (e.g., real-time versus non-real-time, formally verified versus non-formally verified) described above are non-exhaustive examples of different characteristics that may be associated with different operating systems. In other embodiments, two operating systems may have different security characteristics, two operating systems may provide interfaces to different sets of hardware, two operating systems may provide different structures for data management, and so on. In fact, different operating systems may be associated with many additional differing characteristics.

In view of the explanations set forth above, readers will recognize that the benefits of device operation across multiple operating system modalities according to embodiments of the present invention include:

-   -   Separation of device initialization code and device operational         code into separate unverified and verified operating systems,         thereby minimizing the amount of device code subject to formal         verification. This reduces the computational and manpower         resources required to formally verify the operating system and         the corresponding device code.     -   A reduction in the amount of hardware required in an autonomous         vehicle as the same hardware, through OS switching, can support         the execution of different modalities. For example, the same         hardware resources can be used to run an entertainment center or         the control system for the autonomous vehicle, rather than         requiring different hardware systems.

Exemplary embodiments of the present invention are described largely in the context of a fully functional computer system for device operation across multiple operating system modalities. Readers of skill in the art will recognize, however, that the present invention also may be embodied in a computer program product disposed upon computer readable storage media for use with any suitable data processing system. Such computer readable storage media may be any storage medium for machine-readable information, including magnetic media, optical media, or other suitable media. Examples of such media include magnetic disks in hard drives or diskettes, compact disks for optical drives, magnetic tape, and others as will occur to those of skill in the art. Persons skilled in the art will immediately recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a computer program product. Persons skilled in the art will recognize also that, although some of the exemplary embodiments described in this specification are oriented to software installed and executing on computer hardware, nevertheless, alternative embodiments implemented as firmware or as hardware are well within the scope of the present invention.

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

It will be understood that any of the functionality or approaches set forth herein may be facilitated at least in part by artificial intelligence applications, including machine learning applications, big data analytics applications, deep learning, and other techniques. Applications of such techniques may include: machine and vehicular object detection, identification and avoidance; visual recognition, classification and tagging; algorithmic financial trading strategy performance management; simultaneous localization and mapping; predictive maintenance of high-value machinery; prevention against cyber security threats, expertise automation; image recognition and classification; question answering; robotics; text analytics (extraction, classification) and text generation and translation; and many others.

It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims. 

What is claimed is:
 1. A method for device initialization by an access-restricted virtual machine, comprising: restricting access by a first operating system to a device during one or more device initialization operations, wherein the first operating system is executing in a first virtual machine supported by a hypervisor; determining, by a second operating system executing in a second virtual machine supported by the hypervisor, one or more modifications attempted by the first operating system to the device; performing, by the second operating system, the one or more modifications to the device; and performing one or more operations using the device in an initialized state.
 2. The method of claim 1, wherein determining, by the second operating system, the one or more modifications comprises receiving, in response to a fault handling operation, an indication of the one or more attempted modifications.
 3. The method of claim 1, wherein the one or more modifications attempted by the first operating system are included in the one or more device initialization operations.
 4. The method of claim 1, wherein the first virtual machine, and the second virtual machine are implemented by an autonomous vehicle.
 5. The method of claim 1, wherein the first operating system is a non-verified operating system, and the second operating system is a formally verified operating system.
 6. The method of claim 1, further comprising determining, after performing the one or more modifications by the second operating system, that the device is in an initialized state.
 7. The method of claim 6, wherein determining that the device is in an initialized state comprises determining, by the second operating, that the device is in an initialized state, and the method further comprises indicating, by the second operating system to a hypervisor, that the device is in an initialized state.
 8. An apparatus comprising at least one processor and memory storing instructions that, when executed, cause the at least one processor to perform steps comprising: restricting access by a first operating system to a device during one or more device initialization operations, wherein the first operating system is executing in a first virtual machine supported by a hypervisor; determining, by a second operating system executing in a second virtual machine supported by the hypervisor, one or more modifications attempted by the first operating system to the device; performing, by the second operating system, the one or more modifications to the device; and performing one or more operations using the device in an initialized state.
 9. The apparatus of claim 8, wherein determining, by the second operating system, the one or more modifications comprises receiving, in response to a fault handling operation, an indication of the one or more attempted modifications.
 10. The apparatus of claim 8, wherein the one or more modifications attempted by the first operating system are included in the one or more device initialization operations.
 11. The apparatus of claim 8, wherein the first virtual machine, and the second virtual machine are implemented by an autonomous vehicle.
 12. The apparatus of claim 8, wherein the first operating system is a non-verified operating system, and the second operating system is a formally verified operating system.
 13. The apparatus of claim 8, wherein the steps further comprise determining, after performing the one or more modifications by the second operating system, that the device is in an initialized state.
 14. The apparatus of claim 13, wherein determining that the device is in an initialized state comprises determining, by the second operating, that the device is in an initialized state, and the steps further comprise indicating, by the second operating system to a hypervisor, that the device is in an initialized state.
 15. An autonomous vehicle configured for device initialization by an access-restricted virtual machine, the autonomous vehicle comprising an apparatus configured to perform steps comprising: restricting access by a first operating system to a device during one or more device initialization operations, wherein the first operating system is executing in a first virtual machine supported by a hypervisor; determining, by a second operating system executing in a second virtual machine supported by the hypervisor, one or more modifications attempted by the first operating system to the device; performing, by the second operating system, the one or more modifications to the device; and performing one or more operations using the device in an initialized state.
 16. The autonomous vehicle of claim 15, wherein determining, by the second operating system, the one or more modifications comprises receiving, in response to a fault handling operation, an indication of the one or more attempted modifications.
 17. The autonomous vehicle of claim 15, wherein the one or more modifications attempted by the first operating system are included in the one or more device initialization operations.
 18. The autonomous vehicle of claim 15, wherein the first operating system is a non-verified operating system, and the second operating system is a formally verified operating system.
 19. The autonomous vehicle of claim 15, wherein the steps further comprise determining, after performing the one or more modifications by the second operating system, that the device is in an initialized state.
 20. A computer program product stored in a non-transitory computer readable medium, the computer program product comprising computer program instructions for device initialization by an access-restricted virtual machine that, when executed, cause a computer system to carry out steps comprising: restricting access by a first operating system to a device during one or more device initialization operations, wherein the first operating system is executing in a first virtual machine supported by a hypervisor; determining, by a second operating system executing in a second virtual machine supported by the hypervisor, one or more modifications attempted by the first operating system to the device; performing one or more operations using the device in an initialized state. 